feat(projects): implement project center and asset library - #119

Project transport mapping must stay aligned with the backend contract.

Cover pagination, DTO mapping, writes, deletion, and bearer token injection.

Contract regressions fail before reaching the project pages.

The asset library needs the persisted character hierarchy from PR 75.

Map character, outfit, action, and frame data with complete tree updates.

Pages can browse formal assets without generated or mock-only fields.

Character tree mapping carries the core project asset contract.

Cover list, detail, create, update, delete, and token-aware requests.

Nested asset serialization remains protected by executable tests.

Pages consume entities through the layer public entry point.

Export the implemented project and character APIs with their domain types.

Project pages keep respecting the existing dependency boundary.

Backend project and character lists can span multiple pages.

Add a business-neutral pagination control and export it from shared UI.

List pages can navigate all records without duplicating controls.

Projects need an entry page and a persistent project-level workspace.

Implement paged project browsing, deletion, navigation, and project constraints.

Users can enter one project before managing its contained assets.

Project assets need formal browsing below the project workspace.

Implement character cards, outfit selection, stacked actions, and frame expansion.

The UI reflects only fields persisted by the character contract.

Project pages require a nested route boundary outside the global shell.

Mount the asset library and character detail beneath the project workspace.

Direct routes preserve project context without duplicating global navigation.

Project navigation currently changes state without visual continuity.

Add restrained entry, route, dialog, and card transitions with reduced motion.

Page changes remain legible without changing the established palette.

Page tests need realistic HTTP responses without production mock data.

Provide a test-only Project and Character backend with configurable pagination.

Production bundles remain independent from demonstration fixtures.

Project entry and workspace behavior need route-level regression coverage.

Cover real HTTP data, deletion, pagination, constraints, and disabled boundaries.

The project navigation flow remains verifiable without browser fixtures.

Asset browsing must preserve project ownership and frame ordering.

Cover pagination, empty states, outfits, stacked actions, and frame expansion.

Unsupported template and export actions stay explicit and inert.

The architecture documents still describe project pages as placeholders.

Record the formal workspace, backend mappings, merge order, and excluded flows.

Reviewers can distinguish current behavior from backend and future work.